Skip to content

Add skill for pull requests#2292

Closed
bdice wants to merge 1 commit into
rapidsai:mainfrom
bdice:skill-pull-requests
Closed

Add skill for pull requests#2292
bdice wants to merge 1 commit into
rapidsai:mainfrom
bdice:skill-pull-requests

Conversation

@bdice

@bdice bdice commented Mar 12, 2026

Copy link
Copy Markdown
Collaborator

Description

I am experimenting with agent skills, and would like to solve a specific pain point: my agent-generated pull requests haven't been following the PR template and often don't have issues. I would like to help automate some of this and keep agents to a common standard.

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@coderabbitai

coderabbitai Bot commented Mar 12, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c05b4a90-9584-40d6-8746-10af1d755e01

📥 Commits

Reviewing files that changed from the base of the PR and between 22d812c and 5582546.

📒 Files selected for processing (1)
  • .agents/skills/pull-requests/SKILL.md

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Added pull request guidelines including standards for PR titles, descriptions, branching practices, and issue references.

Walkthrough

A new skill definition file is added to configure pull request guidelines, specifying rules for branching, PR descriptions, issue referencing, and CHANGELOG compatibility for the rapidsai/rmm repository.

Changes

Cohort / File(s) Summary
Skill Definition
.agents/skills/pull-requests/SKILL.md
New file with YAML front matter defining the pull-requests skill, including rules for branch targeting, fork usage, PR description template adherence, concise titling for CHANGELOG, and mandatory issue referencing (existing or newly created).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add skill for pull requests' is concise and directly describes the main change—adding a new skill file for pull request automation.
Description check ✅ Passed The description is clearly related to the changeset, explaining the motivation for adding the pull request skill and its intended purpose.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can get early access to new features in CodeRabbit.

Enable the early_access setting to enable early access features such as new models, tools, and more.

@bdice

bdice commented Mar 13, 2026

Copy link
Copy Markdown
Collaborator Author

I checked what the agent can see, and it seems fine:

Prompt

Confirm what skills you have

Response

I have one specialized skill:

pull-requests

For creating and managing pull requests against rapidsai/rmm. Key behaviors:

  • Targets main branch by default
  • Pushes to the user's fork, not upstream
  • Follows the repo's PR template (.github/pull\_request\_template.md)
  • Ensures every PR references an issue (creates one if needed)
  • Keeps PR titles concise (they appear in the CHANGELOG)

Beyond this skill, I have general capabilities for working with the RMM codebase as described in the project's AGENTS.md:

  • Building: build-rmm-cpp, build-rmm-python, build-rmm (devcontainer), or build.sh / CMake directly
  • Testing: C++ (GoogleTest via ctest), Python (pytest)
  • Linting/Formatting: pre-commit run --all-files
  • Code exploration: searching, reading, and editing files
  • Git operations: commits, branches, diffs, logs
  • GitHub operations: via gh CLI (issues, PRs, checks, releases)

@bdice

bdice commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator Author

I no longer think this is important. My agents have been better-behaved recently. Happy to revisit if others think it would be helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants